翻訳と辞書
Words near each other
・ Holland House, Cardiff
・ Holland I
・ Holland III
・ Holland Independent School District
・ Holland Island
・ Holland Island Bar Light
・ Holland Jenks House
・ Holland Junior/Senior High School
・ Holland Ladies Tour
・ Holland Land Company
・ Holishkes
・ Holism
・ Holism (disambiguation)
・ Holism in science
・ Holistic community
Holistic Data Management
・ Holistic dentistry
・ Holistic Design
・ Holistic education
・ Holistic grading
・ Holistic health
・ Holistic Image VIII
・ Holistic Information Security Practitioner
・ Holistic management (agriculture)
・ Holistic Management International
・ Holistic Moms Network
・ Holistic nursing
・ Holistic veterinary medicine
・ Holit
・ Holitman Drive (Ottawa)


Dictionary Lists
翻訳と辞書 辞書検索 [ 開発暫定版 ]
スポンサード リンク

Holistic Data Management : ウィキペディア英語版
Holistic Data Management
Holistic Data Management (HDM) framework is AHISDATA indigenous standard for implementing software implementations within an organization network. This framework extends the existing data management solutions such as data quality, data governance, data integration, data processing, master data management and data validation solutions.
The HDM framework specifies that:
*All data objects must exist as a child data object or a parent data object.
*Only one unique parent data object must exist within a data network scope (DNS).
*All child data objects must have a data-mapping link defined within a data network scope.
*A data object relationship must exist at least in one of the following four data management modules:
''Data mapping'', ''data validation'', ''data integration'',''data processing''
== HDM framework ==
The following entities are specified in the HDM framework.
*''Data network scope (DNS)''
The data network scope (DNS) is the logical boundary that a software application database system of record (SOR) exists within an enterprise network. There can be multiple DNS within an enterprise network.
*''Data network domain (DND)''
The data network domain (DND) is the logical boundary representing a collection of multiple data network scope (DNS). There can be multiple DND within an enterprise network.
*''System of record (SOR)''
A system of record applies to the master or principal database system that a parent data objects resides on.
There can only be one SOR within a data network scope.
*''Parent data object (PDO)''
A parent data object (PDO) is the system of record schema object name. Only one unique parent data object must exist within a data network scope.
*''Child data object (CDO)''
A child data object (CDO) is a schema object name that derives its data from one or more parent data object(s).
*''Data-mapping link (DML)''
A data-mapping link (DML) is the data requirement specification applied to the relationship between multiple database schema objects where one data object derives its data from one or more data objects. DML is only applicable for a data-mapping data management module.
*''Data–object relationship (DOR)''
The data–object relationship (DOR) is the data requirement, business rule, program function that applies to one or multiple data objects. DOR can be applied on data-mapping links for each data management modules. Only one DOR can exist on a DML within a data management module.
*''Data management modules (DMM)''
Data management modules are the common user interface (UI) programs that defines and manage the data object relationship(s) within a data network scope.
There are four data management modules:
''Data mapping'' – This is the base data management user interface module. The data-mapping module provide the functionalities for managing data-mapping links and data object relationships for all database schemas within a data network scope. A data network scope must have at least one data-mapping design defined.
''Data validation'' – This user interface module provides the functionalities for defining and managing validation events on data object relationships. Validation events include auditing, reporting, scheduler, logger, triggers and DNS health check. Data validation events requires a data-mapping design defined within a data network scope.
''Data integration'' – This user interface module provides the functionalities for defining and managing interface configurations on data object relationships. The interface configurations include scheduler, transmission mode, listener, interface API and reporting. The interface APIs would allow third-party systems to transfer data using the data object relationship defined within a data network scope. Data Integration interface configuration requires a Data Mapping design defined within a data network scope.
''Data processing'' – This user interface module provides the functionalities for defining and managing interface configurations and batch runtime engines on data object relationships. The interface configurations include scheduler, transmission mode, multi-batch transmission, user-defined DOR API and reporting. Data Processing interface configuration requires a data-mapping design defined within a data network scope.

抄文引用元・出典: フリー百科事典『 ウィキペディア(Wikipedia)
ウィキペディアで「Holistic Data Management」の詳細全文を読む



スポンサード リンク
翻訳と辞書 : 翻訳のためのインターネットリソース

Copyright(C) kotoba.ne.jp 1997-2016. All Rights Reserved.